Visual Patterns in Issue Tracking Data

Software development teams gather valuable data about features and bugs in issue tracking systems. This information can be used to measure and improve the efficiency and effectiveness of the development process. In this paper we present an approach that harnesses the extraordinary capability of the human brain to detect visual patterns. We specify generic visual process patterns that can be found in issue tracking data. With these patterns we can analyze information about effort estimation, and the length, and sequence of problem resolution activities. In an industrial case study we apply our interactive tool to identify instances of these patterns and discuss our observations. Our approach was validated through extensive discussions with multiple project managers and developers, as well as feedback from the project review board. Posted at the Zurich Open Repository and Archive, University of Zurich ZORA URL: https://doi.org/10.5167/uzh-42658 Originally published at: Knab, P; Pinzger, M; Gall, H C (2010). Visual patterns in issue tracking data. In: International Conference on Software Process, Paderborn, Germany, 8 July 2010 9 July 2010, 222-233. Visual Patterns in Issue Tracking Data Patrick Knab1, Martin Pinzger2, and Harald C. Gall1 1 Department of Informatics, University of Zurich, Switzerland [email protected], [email protected] 2 Department of Software Technology, Delft University of Technology, The Netherlands [email protected] Abstract. Software development teams gather valuable data about feaSoftware development teams gather valuable data about features and bugs in issue tracking systems. This information can be used to measure and improve the efficiency and effectiveness of the development process. In this paper we present an approach that harnesses the extraordinary capability of the human brain to detect visual patterns. We specify generic visual process patterns that can be found in issue tracking data. With these patterns we can analyze information about effort estimation, and the length, and sequence of problem resolution activities. In an industrial case study we apply our interactive tool to identify instances of these patterns and discuss our observations. Our approach was validated through extensive discussions with multiple project managers and developers, as well as feedback from the project review board.